POV-Ray : Newsgroups : povray.binaries.images : The Pov-Ray Include File Initiative - Metals.inc Update : The Pov-Ray Include File Initiative - Metals.inc Update Server Time
5 Nov 2024 13:24:36 EST (-0500)
  The Pov-Ray Include File Initiative - Metals.inc Update  
From: [GDS|Entropy]
Date: 12 Apr 2009 05:45:13
Message: <49e1b829@news.povray.org>
Hello,

Sorry for lack of updates recently; got a new GF...and you know how 
consuming those can be. :-)

Before I proceed with the currently nonexistent waters.inc and 
waterSurfaces.inc, I have a few questions that I wish to pose to the 
community.

1) how should I handle materials? Those weren't typically used in the .inc 
files before, and it could be confusing to users calling textures when 
confronted with a surprise material.

2) there have been a few suggestions as to the method of handling radiosity 
compatibility. How should I do this? I had intended on zeroing ambient, but 
there was a thread in which an emissive (needs new keyword due to media 
conflict) property was defined. Though a good idea, can this be implemented? 
If not, then I think I should just zero ambient as planned. Another method 
from Christian F. defined a macro on/off for ambient. Is there a consensus? 
Should I post a survey to my site or something?

That's about it for now.

I'm going to proceed with waters.inc under a new post, and I thank all 
members who submitted metal textures. If you have more, go for it and post 
them under the metals.inc thread.

As a side note I am writing a simple prog to store textures in an xml file 
with pre rendered pictures displayed on demand. This might progress to 
integration with povray, who knows...right now its just meant to organize 
submitted textures and dump them to include files. If I end up adding much 
more to this and it becomes useful, I just may open source it and post it as 
a utility. A HDD search feature would be nice but I'm not likely to 
implement that...I'd hate to have to write that regex.. O_o'

ian


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.